docs: fix internal links pointing at redirecting URLs (post-migration follow-through) - #21117
Open
workprentice[bot] wants to merge 1 commit into
Open
docs: fix internal links pointing at redirecting URLs (post-migration follow-through)#21117workprentice[bot] wants to merge 1 commit into
workprentice[bot] wants to merge 1 commit into
Conversation
Several blog posts and the pricing page link internally through URLs that now 301-redirect to a newer path (the get-started/download-install, guides/continuous-delivery, comparisons/cloud-template-transpilers, support/debugging, pulumi_stack_init, and product/pulumi-cloud migrations). Point every internal link at its final destination instead, so crawlers and readers reach the target in one hop. No sitemap or canonical changes were needed; both were already clean. Verified with the repo's markdown lint and prettier checks.
github-actions
Bot
added
review:triaging
Collaborator
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
🧹 Optional style suggestions from the pre-merge review — apply or dismiss; none of them block.
Generated by Claude Code
| Data replication is important for ensuring the resilience and performance of stateful distributed services. This article not only emphasized the significance of data replication in distributed systems, but it also demonstrated how Pulumi, in collaboration with Azure, enables developers to architect and manage resilient, performant, and globally distributed infrastructures for their stateful applications. As cloud-native architectures expand, the importance of infrastructure as code (IaC) in ensuring optimal data replication outcomes becomes increasingly important, and Pulumi can be used to provision the infrastructure required. | ||
|
|
||
| Did you learn something new? We’d like to know. If you’d like to try this out for yourself, you can get started with Pulumi Cloud [here](/product/pulumi-cloud/). You can also join our community to be a part of the continuous conversation, and we can’t wait to see what you build! | ||
| Did you learn something new? We’d like to know. If you’d like to try this out for yourself, you can get started with Pulumi Cloud [here](/product/). You can also join our community to be a part of the continuous conversation, and we can’t wait to see what you build! |
Contributor
There was a problem hiding this comment.
[style] vague link text — Link text should name the destination
Suggested change
| Did you learn something new? We’d like to know. If you’d like to try this out for yourself, you can get started with Pulumi Cloud [here](/product/). You can also join our community to be a part of the continuous conversation, and we can’t wait to see what you build! | |
| Did you learn something new? We’d like to know. If you’d like to try this out for yourself, you can [get started with Pulumi Cloud](/product/). You can also join our community to be a part of the continuous conversation, and we can’t wait to see what you build! |
Contributor
Pre-merge Review — Last updated 2026-08-25T12:41:20ZTip Summary: This is a link-hygiene sweep: 19 internal links across 16 blog posts, one IaC docs page, and the pricing FAQ are repointed from redirecting URLs to their current destinations. The bulk of it is Review confidence:
Investigation log
✏️ 1 one-click style suggestion is posted inline — apply it from the Files changed tab. 🔍 Verification trail53 claims extracted · 34 verified · 3 unverifiable · 2 contradicted
📊 Editorial balanceSingle-subject post; balance check N/A. 🚨 Outstanding in this PRThese must be resolved or refuted before merging.
|
github-actions
Bot
added
review:outstanding-issues
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Following the recent URL restructuring (install docs, CI/CD guides, comparisons, debugging docs, CLI command reference, and the product page), several internal links across blog posts and the pricing page still pointed at the old, now-redirecting URLs instead of their final destinations.
This PR updates each internal link to point directly at the final URL:
/docs/get-started/download-install/->/docs/install//docs/iac/guides/continuous-delivery/pulumi-kubernetes-operator/->/docs/integrations/clouds/kubernetes/pulumi-kubernetes-operator//docs/support/debugging/logging/->/docs/iac/operations/debugging/logging//docs/iac/cli/commands/pulumi_stack_init/->/docs/iac/cli/commands/pulumi_stack_new//product/pulumi-cloud/->/product/(the majority of the changes here, across ~13 blog posts and the pricing FAQ)Why this matters: a link that resolves through a redirect still reaches the reader, but it dilutes crawl efficiency and link-equity flow versus linking straight at the canonical target, and it's simple hygiene to clean up once a migration's redirects are confirmed stable. I verified each of the underlying 301s is a clean single hop with a self-referential canonical on the destination page, and confirmed the sitemap already lists only the new URLs, so this PR is scoped purely to the remaining internal-link references. No sitemap, canonical, or template changes were needed.
Verified with the repo's markdown lint (
node ./scripts/lint/lint-markdown.js, 0 errors) andprettier --checkon every changed file; both pass cleanly, and the pre-commit hook ran the same lint automatically.🧠 This PR was created by workprentice.